home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Monster Media 1996 #15
/
Monster Media Number 15 (Monster Media)(July 1996).ISO
/
renegade
/
usere130.zip
/
OERRORS.TXT
< prev
next >
Wrap
Text File
|
1994-08-01
|
4KB
|
78 lines
Various Runtime Errors you may get when running OILERSoFT utilities
and there explanation. If you have any questions or need any help at
all just give my BBS a call at 702-629-0723:
Number Meaning What the problem 'Could' be
------ ----------------------- -------------------------------------------
2 File not found You are missing a file, or are specifying
a file in a configuration file that does
not exist.
3 Path not found You are specifying a path that does not
exist.
4 Too many open files Increase your FILES= statement in your
CONFIG.SYS I recommend about 30-50.
5 File access denied Either a file has been set to read only, a
directory is full, a RENAME tried to rename
to an existing file name or a file is not
open.
6 Invalid File Handle Your file handles have become corrupted.
100 Disk Read Error An attempt was made to read past the end of
a file. Most often something is corrupted
in the record pointers of a data file.
101 Disk Write Error Generally an indication of a full hard disk.
103 File Not Open File is closed when it shouldn't have been.
104 File Not Open f/Input Text file is closed when it shouldn't
have been.
105 File Not Open f/Output Text file is closed when it shouldn't
have been.
106 Invalid Numeric Format Generally this is only caused when reading a
configuration file, and the program is
expecting to find a numeric value and it
does not.
Errors 150 through 162 indicate various HARDWARE failures. If you're
getting these, then something may be wrong with your PC.
Number Meaning What the problem 'Could' be
------ ----------------------- -------------------------------------------
152 Drive not ready Controller problem or drive not spinning.
154 CRC error in data Sector on your drive may be damaged.
156 Disk Seek error Head problem or bad controller.
157 Unknown media type Computer cannot read the media type you
have. Is the drive formatted?
158 Sector not found Head problem or bad controller.
159 Printer out of paper Install more paper.
160 Device write fault Disk problem
161 Device read fault Disk problem
162 Hardware Failure Reported due to Dos sharing violations.
If you run Multi-Node make sure 'Share'
is being run. This can also be cured
sometimes by adding more FILES= to your
CONFIG.SYS file. Try 30-50.
Fatal errors generally indicate a problem that must be fixed before you
can continue to run the utility.
Number Meaning What the problem 'Could' be
------ ----------------------- -------------------------------------------
200 Division by zero Should never happen, but if it does, report
it to me at OILERSoFT.
201 Range Check Error Array index out of range.
202 Stack Overflow NOT ENOUGH MEMORY for the stack!.
203 Heap overflow error Same as 202.
204 Invalid Pointer Op. Can be caused the same as 202.
205 Floating point overflow Should not happen, unless a utility gets
a bad number from a data file.
207 Invalid Floating point
Operation Same as 205.
209 Overlay File read error If you're not using EMS, then the .OVR
file is missing or is setting on a bad
sector on your harddisk. If you are
running EMS then you may have a bad
memory chip!
Again, if you have any problems with a utility do not hesitate to contact
me at The Coliseum BBS (Home of OILERSoFT) at 702-629-0723.